翻訳と辞書
Words near each other
・ Amiga A570
・ Amiga Action
・ Amiga Active
・ Amiga Advanced Architecture chipset
・ Amiga Advanced Graphics Architecture
・ Amiga CD32
・ Amiga Chip RAM
・ Amiga Computing
・ Amiga Corporation
・ Amiga custom chips
・ Amiga demos
・ Amiga Disk File
・ Amiga E
・ Amiga emulation
・ Amiga Enhanced Chip Set
Amiga Fast File System
・ Amiga Force
・ Amiga Forever
・ Amiga Format
・ Amiga Games Database
・ Amiga Halfbrite mode
・ Amiga Hombre chipset
・ Amiga Hunk
・ Amiga models and variants
・ Amiga music software
・ Amiga Mía
・ Amiga Old File System
・ Amiga Power
・ Amiga productivity software
・ Amiga programming languages


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Amiga Fast File System : ウィキペディア英語版
Amiga Fast File System

The Amiga Fast File System (FFS; not to be confused with the identically named Berkeley Unix FFS) is a file system used on the Amiga personal computer. The previous Amiga filesystem (known originally simply as "DOS" or AmigaDOS) upon the release of FFS became known as Amiga Old File System (OFS). OFS, while fine on floppy disk, soon proved too slow to keep up with era hard drives. FFS was designed as a full replacement for the original Amiga filesystem.
FFS differs from its predecessor mainly in the removal of redundant information. Data blocks contain nothing but data, allowing the filesystem to manage the transfer of large chunks of data directly from the host adapter to the final destination.
==Characteristics==
OFS was the predecessor to FFS. Before FFS was released, AmigaOS had a single filesystem simply called AmigaDOS: this used 24 bytes per sector for redundancy data, providing for reconstructing structural data on less reliable media such as floppy disks. When higher speed media (i.e. hard disks) became more available to the Amiga, this redundant data posed a bottleneck as all data needed to be realigned to be passed to the application. So the redundancy was removed for FFS and the data read in from media could be passed to the application directly. The previous filesystem, AmigaDOS, was renamed OFS, Old File System, to differentiate between it and FFS. FFS was backward compatible and could access devices formatted with OFS.
Given these advantages, FFS was rapidly adopted as the filesystem used by almost all Amiga users, although OFS continued to be widely used on floppy disks from third party software vendors. This was purely for compatibility with pre-AmigaOS 2 systems in games and applications that did not actually require AmigaOS 2+, as machines running earlier versions of the OS without FFS in the ROM could not boot from these floppies, although they could still read them if they had FFS installed.
Amiga FFS is simple and efficient, and when introduced was more than adequate, and had many advantages compared to the file systems of other platforms. However, as OFS had done before it, it aged; as drives became larger and the number of files on them increased, its use as a day-to-day filesystem became more problematic in terms of difficulty of maintenance and competitiveness of general performance. Despite this, it is still used on AmigaOS systems even today according to users of these systems.
By the last Commodore release of AmigaOS, 3.1, FFS was still the only filesystem shipped as standard with the Amiga, but was already showing its age as technology advanced. FFS (and OFS) stores a "bitmap" of the filesystem in a single sector. On write, this is first marked as invalid, then the write is completed, then the bitmap updated and marked as valid. If a write operation is interrupted by a crash or disk removal, this then allows the 'disk-validator' program to undo the damage. This is a very simple form of filesystem journaling. To allow the disk to be used again, the entire disk has to be completely scanned and the bitmap rebuilt, but only the data being modified during the write would be lost. During this scanning the disk cannot be written to by anything but disk-validator, and read access is very slow.
AmigaOS originally included a disk-validator on every bootable disk, which was unfortunately prone to being replaced by viruses to allow themselves to spread (for example the "Saddam Hussein" virus). Later and more sensibly, it became part of the ROM from Kickstart 2.x onwards, protecting it from malicious replacement. The disk-validator attempted to repair the bitmap on an invalidated drive by write-protecting the drive and scanning it; this could take a long time and made it very slow to access the disk until it was finished, especially on slower media. As hard drives got larger and contained more files, the validation process could take many hours. In addition, files and directories could feasibly be lost (often without user being notified or even aware) during the process if their data hashes were corrupted. In some cases the validator could even fail, forcing the user to use a third-party disk tool like DiskSalv to make the volume writable again, or simply save the files by copying them to a fresh partition, a very slow process.
FFS was also originally limited to 32-bit addressing and therefore about 4 GB drives. Attempting to use FFS partitions beyond this limit caused serious data corruption all through the drive. FFS belatedly got some third-party 64-bit patches and then official (but non-Commodore) updates to allow it to circumvent these limitations. The latter were supplied with AmigaOS 3.5 and 3.9, from Haage & Partner. The former often were supplied with third party disk controllers, where the ability to use large capacity disks was a selling point.
In terms of support tools, although Commodore itself only shipped with an application called DiskDoctor (and later removed it from AmigaOS disks), FFS had a small selection of third-party tools -- most notably DiskSalv -- to maintain the file system and repair and validate it, undelete files, or reverse "quick formats" (filesystem initializations). An OFS or FFS volume had to be locked to defragment or convert to different FFS modes to prevent corruption and this made it inaccessible to everything but the tool defragmenting it. Most of these tools were not updated when FFS became capable of 64-bit addressing and could only operate on drives smaller than 4 GB of the drive; they could not read partitions bigger than 4 GB, and would generally corrupt partitions "beyond" the 4 GB boundary. When hard drives in use by Amiga users were reaching 4 GB in size, this obviously became a real problem.
For all of these reasons, FFS was often being replaced by users in the mid-1990s with more up to date alternatives such as Smart File System (SFS) and Professional File System (PFS), which did not have these limitations and were considered safer, faster and more efficient. SFS in particular kept being developed and now as close to a generic AmigaOS filesystem as FFS is.

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Amiga Fast File System」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.